Update metalsmith → 2.6.0 (unknown) #117
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ metalsmith (2.5.1 → 2.6.0) · Repo · Changelog
Release Notes
2.6.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Release 2.6.0Prepare changelog for 2.6.0Removes stray cross-spawn dependency & use --no-package-lock for CItest: migrate from nyc to c8 for coverage reportstypes: fix source code link line numbersfeat/#379 - use lodash.clonedeepwith instead, document watch type, fix issues in CLIResolves #379: add metalsmith.watch option setter and watcherfix: package.json node version, type docs, readme formattingtest: fix FS race condition in #build should return a promise only when callback omitteddocs: Updates readme examples to ESM & Gitter link to Matrix ElementCLI: Fix ESM dynamic import issue with absolute paths on WindowsAdds CLI support & tests for loading ESM configs or Metalsmith instancesci: remove Node 12, add Node 20Updates commander from 8.3.0 -> 10.0.1Removes rimraf dependency, refactors helpers using fs/promises and upgrades @types/nodeDrops support for Node < 14chore: Remove stray console.error log in binTrims whitespace from parsed front-matter excerpt and adds test for dynamic front-matter langFix: don't keep gray-matter excerpt at the start of file contentsAdds a matter member object to metalsmith instance with stringify & parse methodsSupport 'module.exports = Metalsmith()'-style configs in CLIdev: update devDependencies & fix security warningsci: remove obsolete Gitter notification flowResolves #356: adds Typescript support to Metalsmith packagetest: fix concurrency issue in multi-build test using the same dest dirdev: update devDependencies to latest & replace eslint-plugin-nodeFixes a duplicate empty input check in metalsmith.match & adds a test for falsy inputAdded Metalsmith CLI support for loading a .(c)js config. Reads from metalsmith.js as second default after metalsmith.jsonCLI reads JSON config instead of requiring it. This allows pre-processing the config as string and paves the way for import compat.Adds --env option to metalsmith (build) commandAdds --debug and --dry-run options to metalsmith (build) commandUpgrades CLI commander 6.2.1 -> 8.3.0 and modernizes Metalsmith CLIUpgrade commander to latest Node 12 compatible👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands